Content Packages

Use content packages to reduce the content that is available to users.

Overview

Content packages allow you to specify, at a granular level, the content that is available to users in different parts of the solution experience. With content packages you can control:

  • The Guidebooks that are available to users, and the topics and analyses that users see in the Guidebook.
  • The metrics, dimensions, and key groups that are available to users when conducting ad hoc analysis.
  • The plan models that planners can create plans for.

Content packages are not part of data security because they don't allow you to hide content from all user workflows. While content packages do hide things from the user’s view, they do not exclude them from places like the Detailed View visual. Different content packages can be assigned to each permission.

Example: Hide content using a content package

Let's say that you create a content package that excludes all Retention metrics (for example, Exit Count). Then you apply this content package to a user who has data access to everything. When the content package is applied, this user will not see any Retention metrics in the Metric picker when conducting ad hoc analysis in Explore. However, as long as this user has data access to these metrics, they will still see Retention metrics that are used in Guidebook analyses.

You will have to update your content packages whenever new content (Guidebooks, analyses, metrics, dimensions, and key groups) is created in the studio experience and published to production. By default, new content is automatically hidden in content packages. For example, when you publish a new analysis to production, you will need to make the analysis visible in the content packages so they're accessible in the solution experience and users can see them in the Guidebook. If you don't want to manually update the content packages each time, we recommend that you use the Visier - All Content content package, which provides access to the complete set of Visier content and any new customized content that is created. You should assign this content package to any user who will be creating content in the studio experience to ensure they can successfully use and edit newly added content when working in a project.

Use cases for content packages

These are some of the situations when you should use content packages.

Improve the user experience

There are many metrics and attributes that come with the solution and some users may only need a portion of this content. Users may only require a subset of these metrics, groupings, and filters. So remove unneeded content from the Metric picker and Dimensions list to improve the user experience and allow users to find what they need quicker.

Manage the user rollout

When you introduce the solution to new users, you may want to focus your training on a small portion of the metrics, groupings, and filters. This will allow you to reduce training time and get your audience up and running faster. While it’s good to simplify the user experience, you may not want to do so using security. Instead, set up your security for the long-term perspective by including everything users will access and use in the future and limit what they can see for now by using a content package. Gradually introduce new attributes and metrics to users over time by enabling new items in their content package without constantly having to revisit your security model.

Hide metrics that cannot be removed via data security settings

Preventing access to some data can limit a wide range of metrics, which may not be the preferred outcome. For example, if you remove data access to Ethnicity, users will not have access to the Ethnicity attribute and the following metrics:

  • Minority Ratio in US
  • Minority Ratio Variance from My EEOC Benchmark
  • Promotion Rate - Ethnic Minority in US

You may want to remove only certain metrics or attributes from the list. To achieve this, you can leave Ethnicity enabled as part of the user’s data access and use a content package to hide individual metrics or attributes.

In this section